-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup the geos python package CI #4
Conversation
@TotoGaz - any thoughts on the CI configuration? I'm building off of the github template for python packages here. Do you want to add/remove any python versions? Also, I've commented out the linting and testing steps for now, as we haven't been enforcing these yet. |
.github/workflows/python-package.yml
Outdated
strategy: | ||
fail-fast: false | ||
matrix: | ||
python-version: ["3.9", "3.10", "3.11"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to have python 3.8? I kind of remember there are some differences for type hints starting python 3.9.
Those differences were popping errors on ubuntu 20.04 (IIRC) but the differences are not worth ditching 3.8 from the supported platforms.
|
||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: mpi4py/setup-mpi@v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to rely on this or should we prefer installing from requirements.txt
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These help to setup the underlying python and mpi environments (needed for mpi4py to not throw an error). We could probably roll our own, but these actions seem to be quite reliable.
No description provided.